Skip to main content

Add Human Task

AutomatR.OrchestratorActivities.AddHumanTask

The "Add Human Task" activity in AutomatR OrchestratorActivities allows you to incorporate manual intervention in your workflows by sending tasks to users for input. This is particularly useful when a human decision or action is required during the execution of a process.

Properties

NameDescription
Input
Transaction IDSpecifies the unique identifier for the transaction whose status is to be updated. String variables containing the transaction ID.
Send to User (email)Specifies the email ID of the user to whom the task is to be sent. String variables containing the user's email ID.
Form Data FieldsSpecifies custom data in dictionary format that needs to be included in the human task. Dictionary variables containing custom data.
Form NameSpecifies the name of the form associated with the human task. String variables containing the form name.
Misc
Display NameProvides a customizable name for the activity displayed in the workflow. The display name enhances clarity and organization within the automation project. String variable or argument containing the desired display name.
Optional
DelaySpecifies the amount of time (in seconds) to wait before executing the "Add Human Task" activity. This can be useful for handling synchronization issues. Integer variables containing the delay duration. Ex.: If the amount of time is 1000 milliseconds or 1 sec, i.e., 1.
Output
StatusOutputs the result of the "Add Human Task" operation, indicating whether the task addition was successful or encountered errors. Variables of relevant types (e.g., Boolean variables) to store the operation result.

How to use:

  1. Drag and drop the "Add Human Task" activity onto the workflow.
  2. Configure the properties by specifying the transaction ID, user's email ID, custom data, and form name.
  3. Optionally, configure the delay for the desired waiting time before adding the human task.
  4. Execute the workflow to send a task to the specified user, awaiting their input.

Example: Consider an example where the "Add Human Task" activity is used to incorporate manual approval in a workflow:

Add Human Task:
Transaction ID: "123456"
Send to User (email): "john.doe@example.com"
Form Data Fields: { "ApprovalType": "Manager", "Comments": "Please review and approve." }
Form Name: "ApprovalForm"
Status: isTaskAddedSuccessfully

In this example, the activity sends a task with custom data to the user with the email ID "john.doe@example.com" for approval. The result of the operation (success or failure) is stored in the Boolean variable "isTaskAddedSuccessfully" for further handling in the workflow.

Note: Ensure that the "Add Human Task" activity is appropriately integrated into the workflow and that the specified form name aligns with the expected input requirements for the human task.